Data registration system

ABSTRACT

Provided is a data registration system capable of efficiently registering highly effective data related to a vehicle or the like. The data registration system includes an integration processing server and an integrated database server. The integration processing server creates a data mart having an FCD, weather data, vehicle condition data, fuel economy data, navigation data, a vehicle ID, and a user ID which are linked to one another and creates an encrypted data mart by compressing the data mart by the Lzo algorithm and encrypting the compressed data mart. The integrated database server stores the encrypted data mart in a storage region.

BACKGROUND OF THE INVENTION Field of the Invention

The present invention relates to a data registration system forregistering data related to a vehicle or the like input through anetwork.

Description of the Related Art

As a management system for vehicle operation data, one disclosed inJapanese Patent Laid-Open No. 2017-27545 has been known. The managementsystem comprises an on-vehicle device and an operation managementdevice. The on-vehicle device acquires, as operation data, a runningspeed, a running distance, an acceleration, a geographical position, adriving operation, a fuel jet quantity, and the like of a vehicle fromvarious types of devices and various types of sensors of a vehicle.

The on-vehicle device links (associates) operation data to (with)identification information for identification of a driver and stores thedata and the information since the start of operation data acquisition,and transmits each pair of operation data and identification informationlinked together to the operation management device when a finishoperation is performed by a driver.

SUMMARY OF THE INVENTION

There has recently been a need to sequentially register pieces of datato form big data and analyze and utilize the big data in various fields.The same applies to data related to a vehicle or the like. In contrast,the management system in Japanese Patent Laid-Open No. 2017-27545 is notpremised on utilization of pieces of data by forming the pieces of datainto big data and suffers the problem of the incapability of efficientlyregistering highly effective data.

The present invention has been made to solve the above-describedproblem, and has as its object to provide a data registration systemcapable of efficiently registering highly effective data related to avehicle or the like.

In order to attain the above-described object, a data registrationsystem according to the present invention comprises a data receptionunit to which a plurality of types of data and vehicle-identifying datafor identification of at least one of a vehicle and an owner of thevehicle are input through a network, the plurality of types of dataincluding movement status data representing a time-series movementstatus of a mobile station, consumption rate data representing an energyconsumption rate of the vehicle moving together with the mobile station,navigation data representing a navigation computation result and asetting state in the vehicle, and weather data representing weather in aregion in which the mobile station existed; a data group creation unitwhich creates a data group having the movement status data, theconsumption rate data, the navigation data, the weather data, and thevehicle-identifying data that are linked to one another; a registereddata creation unit which compresses the data group by a predeterminedcompression algorithm and creates registered data using the compresseddata group; and a data storage unit which stores the registered data ina storage region.

According to the data registration system, the data group having themovement status data, the consumption rate data, the navigation data,the weather data, and the vehicle-identifying data that are linked toone another is created. In this case, the movement status data, theconsumption rate data, the navigation data, and the weather datarepresent the time-series movement status of the mobile station, theenergy consumption rate of the vehicle moving together with the mobilestation, the navigation computation result and the setting in thevehicle, and the weather in the region that is the previous location ofthe mobile station, respectively, and the vehicle-identifying data isintended to identify the vehicle and/or the user of the vehicle. Thedata group having the data linked to one another is thus highlyeffective at the time of forming pieces of data related to the vehicleor the like into big data and analyzing the big data. Additionally,since the data group is compressed by the predetermined compressionalgorithm, the registered data is created using the compressed datagroup, and the registered data is stored in the storage region, the sizeof a registered data can be reduced. This allows an increase in thenumber of pieces of registered data which can be stored in a storageregion of the same size. With the above-described configuration, highlyeffective data can be efficiently registered (note that a piece ofnavigation data representing a navigation computation result and asetting in a vehicle in the present specification is not limited to apiece of data representing a computation result and a setting in anavigation device mounted on the vehicle and may include a piece of datawhich is transmitted as a computation result to the navigation devicewhen route computation, position computation, and the like are performedin a server or a handheld terminal on the basis of a piece of datareceived from the navigation device of the vehicle).

According to the present invention, preferably, the data group creationunit creates a first data group having the vehicle-identifying data, themovement status data, and the consumption rate data that are linked toone another, a second data group having the vehicle-identifying data,the movement status data, and the navigation data that are linked to oneanother, and a third data group having the movement status data and theweather data that are linked to each other, and creates the data groupusing the first to third data groups.

According to the data registration system, the first data group havingthe movement status data and the consumption rate data that are linkedto each other, the second data group having the movement status data andthe navigation data that are linked to each other, and the third grouphaving the movement status data and the weather data that are linked toeach other are created, and the data group is created using the first tothird data groups. A load at the time of data group creation can be madesmaller than in a case where a data group is created in one operation.

According to the present invention, preferably, the plurality of typesof data further include vehicle condition data representing at least oneof a manufacturing condition and a repair condition of the vehicle, andthe data group creation unit creates the data group by further linkingthe vehicle condition data to the movement status data, the consumptionrate data, the navigation data, the weather data, and thevehicle-identifying data such that the pieces of data are linked to oneanother.

According to the data registration system, the data group is created byfurther linking the vehicle condition data representing at least one ofthe manufacturing condition and the repair condition of the vehicle tothe vehicle-identifying data, the movement status data, the consumptionrate data, the navigation data, and the weather data as the data groupsuch that the pieces of data are linked to one another. This allowsfurther enhancement of the effectiveness of the data group at the timeof forming pieces of data into big data and analyzing the big data.

According to the present invention, preferably, the data group creationunit creates a first data group having the vehicle-identifying data, themovement status data, and the consumption rate data that are linked toone another, a second data group having the vehicle-identifying data,the movement status data, and the navigation data that are linked to oneanother, a third data group having the movement status data and theweather data that are linked to each other, and a fourth data grouphaving the vehicle-identifying data, the movement status data, and thevehicle condition data that are linked to one another, and creates thedata group using the first to fourth data groups.

According to the data registration system, the first data group havingthe movement status data and the consumption rate data that are linkedto each other, the second data group having the movement status data andthe navigation data that are linked to each other, the third data grouphaving the movement status data and the weather data that are linked toeach other, and the fourth data group having the movement status dataand the vehicle condition data that are linked to each other arecreated, and the data group is created using the first to fourth datagroups. A load at the time of data group creation can be made smallerthan in a case where a data group is created in one operation.

According to the present invention, preferably, the movement status dataand the navigation data each comprise a vehicle position at a time ofsampling as a piece of data, and in a case where there are a pluralityof data having a same vehicle position at the time of sampling in themovement status data and the navigation data in a case of creating thesecond data group, the data group creation unit links data which areclosest in the time stamp at the time of sampling to each other amongthe plurality of data.

According to the data registration system, if the movement status dataand the navigation data are not coincident in the vehicle position atthe time of sampling with each other in a case of creating the seconddata group, the one piece of the movement status data and the one pieceof the navigation data that are closest in the vehicle position at thetime of sampling are linked to each other. Thus, the second data groupcan be created by linking pieces of data which are closest in vehicleposition at the time of sampling and are estimated to be highly relatedto each other. This allows enhancement of the accuracy of creating thesecond data group.

According to the present invention, preferably, the movement status dataand the navigation data each comprise a time stamp at the time ofsampling and a vehicle position at the time of sampling as pieces ofdata, in a case where there are a plurality of data having a samevehicle position at the time of sampling in the movement status data andthe navigation data, in the case of creating the second data group, thedata group creation unit links data which are closest in the time stampat the time of sampling to each other among the plurality of data.

According to the data registration system, in the case where there are aplurality of data having the same vehicle position at the time ofsampling in the movement status data and the navigation data, in thecase of creating the second data group, the data that are closest in thetime stamp at the time of sampling are linked to each other among theplurality of data. Thus, the second data group can be created by linkingpieces of data which are closest in time stamp at the time of samplingand are estimated to be highly related to each other. This allowsenhancement of the accuracy of the creation.

Preferably, the registered data creation unit creates the registereddata by encrypting the compressed data group by a predeterminedencryption algorithm.

According to the data registration system, the registered data iscreated by encrypting the compressed data group by the predeterminedencryption algorithm. This allows enhancement of the security of a pieceof registered data.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram schematically showing a configuration of a dataregistration system according to one embodiment of the presentinvention;

FIG. 2 is a flowchart showing a linked data creation process;

FIG. 3 is a flowchart showing a data integration process;

FIG. 4 is a flowchart showing an FCD-navigation provisional data martcreation process;

FIG. 5 is a flowchart showing an encrypted data mart creation process;and

FIG. 6 is a flowchart showing a data storage process.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

A data registration system according to one embodiment of the presentinvention will be described below with reference to the drawings. Asshown in FIG. 1, a data registration system 1 according to the presentembodiment comprises a data processing server 2, an integrationprocessing server 3, and an integrated database server 4.

Each of the servers 2 to 4 comprises a processor, a memory, an I/Ointerface, and the like and is configured to be capable of executingvarious types of arithmetic processing on the basis of an arithmeticprogram in the memory and I/O data.

The data processing server 2 executes a linked data creation process (tobe described later), and the like and stores a large number of pieces ofuser information data in a storage region. Each piece of userinformation data is obtained by linking a piece of personal informationof a user of a vehicle, a user registration date, a user ID, and avehicle ID to one another and is created using the pieces of data whenthe pieces of data are input via an input interface (not shown) by aserver administrator. Note in the present embodiment that the dataprocessing server 2 corresponds to a data reception unit and that a userID and a vehicle ID correspond to a piece of vehicle-identifying data.

A weather server 11, a large number of plants 12 (only one of which isshown), a large number of dealers 13 (only one of which is shown),navigation devices (not shown) of a large number of vehicles 14 (onlyone of which is shown), and the like are connected to the dataprocessing server 2 over a network 10. The various types of pieces ofdata below are input from the elements. Note that the followingdescription assumes that a power source of each vehicle 14 is aninternal combustion engine.

More specifically, a piece of weather data is input from the weatherserver 11 to the data processing server 2. The piece of weather data isobtained by linking a mesh code of a country where a vehicle is used,the weather, a time stamp at the time of measurement of the weather, andthe like to one another.

A piece of manufacturing data is input from each plant 12 to the dataprocessing server 2. The piece of manufacturing data is obtained bylinking a vehicle ID, a time stamp at the time of vehicle manufacture, amanufacturing plant name, a manufacturing lot number of a vehicle, andthe like to one another.

A piece of dealer data is input from each dealer 13 to the dataprocessing server 2. The piece of dealer data is obtained by linking avehicle ID, a time stamp at the time of vehicle maintenance or repair, adealer name, vehicle maintenance details or repair details, and the liketo one another. Note that a piece of manufacturing data and a piece ofdealer data will be collectively called a “piece of vehicle conditiondata” in the following description.

A piece of movement status data, a piece of fuel economy data, and apiece of navigation data are input from the navigation device (mobilestation) of each vehicle 14 to the data processing server 2. The pieceof movement status data, the piece of fuel economy data, and the pieceof navigation data are sampled at predetermined control intervals fromwhen an ignition switch of the vehicle 14 is turned on to when theignition switch is turned off. Results of the sampling are input to thedata processing server 2. In this case, a piece of data sampled at atime when the ignition switch is turned off is input from the navigationdevice to the data processing server 2 at a time when the ignitionswitch is turned on next time.

The piece of movement status data is obtained by linking a position ofthe vehicle 14 which is a position (a longitude and a latitude) of anavigation device, a time stamp at the time of sampling of the position,and a user ID to one another. A piece of movement status data will bereferred to as an “FCD” hereinafter. The piece of fuel economy data isobtained by linking the fuel economy of the vehicle 14, a time stamp atthe time of sampling of the fuel economy, and the user ID to oneanother.

The piece of navigation data is obtained by linking respective settingsfor a departure place and a destination, a result of computing alatitude and a longitude of a current place and a route from thedeparture place to the destination, a time stamp at the time of samplingof the pieces of data, and the user ID in the navigation device of thevehicle 14 to one another.

Note that time stamps included in a piece of weather data, a piece ofvehicle condition data, a piece of movement status data, a piece of fueleconomy data, and a piece of navigation data when the pieces of data areinput will be collectively referred to as “time stamps at the time ofsampling” in the following description.

The data processing server 2 creates a piece of linked data through thelinked data creation process (to be described later) and outputs thepiece of linked data to the integration processing server 3.

The integration processing server 3 creates a data mart using pieces oflinked data input from the data processing server 2 through a dataintegration process (to be described later) and encrypts the data martto create an encrypted data mart, and outputs the encrypted data mart tothe integrated database server 4. Note in the present embodiment thatthe integration processing server 3 corresponds to a data group creationunit and a registered data creation unit and that a data mart and anencrypted data mart correspond to a data group and a piece of registereddata, respectively.

The integrated database server 4 stores an encrypted data mart inputfrom the integration processing server 3 in a storage region, as will bedescribed later.

The linked data creation process described earlier will be describedwith reference to FIG. 2. The process creates pieces of linked datausing various types of pieces of data (i.e., a piece of movement statusdata, a piece of fuel economy data, a piece of navigation data, a pieceof vehicle condition data, and a piece of weather data) input to thedata processing server 2 and outputs the pieces of linked data to theintegration processing server 3, and is executed at predeterminedcontrol intervals ΔT (e.g., 5 minutes) in the data processing server 2.

As shown in FIG. 2, each type of piece of data input to the dataprocessing server 2 is first read (step S1 of FIG. 2). A time stamp atthe time of reading (hereinafter referred to as a “reading time stamp”)is linked to the type of piece of data read (step S2 of FIG. 2).

It is then judged whether a user ID in the piece of data having thereading time stamp linked thereto coincides with a user ID in a piece ofuser information data stored in the data processing server 2 (step S3 ofFIG. 2).

If a result of the judgment is affirmative (YES in step S3 of FIG. 2),i.e., if the piece of data having the reading time stamp linked theretois a piece of data with a user ID (an FCD, a piece of fuel economy data,or a piece of navigation data), a vehicle ID corresponding to a user IDin a coincident piece of user information data is linked to the piece ofdata having the reading time stamp linked thereto (step S4 of FIG. 2).

The piece of linked data (i.e., the FCD, the piece of fuel economy data,or the piece of navigation data) after the above-described linking isoutput to the integration processing server 3 (step S5 of FIG. 2). Afterthat, the present process ends.

On the other hand, if the judgment result is negative (NO in step S3 ofFIG. 2), i.e., if the piece of data having the reading time stamp linkedthereto is a piece of data without a user ID (a piece of vehiclecondition data or a piece of weather data), it is judged whether avehicle ID in the piece of data having the reading time stamp linkedthereto coincides with a vehicle ID in a piece of user information datastored in the data processing server 2 (step S6 of FIG. 2).

If a result of the judgment is affirmative (YES in step S6 of FIG. 2),i.e., if the piece of data having the reading time stamp linked theretois a piece of vehicle condition data with a vehicle ID, a user IDcorresponding to a vehicle ID in a coincident piece of user informationdata is linked to the piece of vehicle condition data (step S7 of FIG.2).

The piece of linked data that is the piece of vehicle condition dataafter the above-described linking is output to the integrationprocessing server 3 (step S5 of FIG. 2). After that, the present processends.

On the other hand, if the judgment result is negative (NO in step S6 ofFIG. 2), i.e., if the piece of data having the reading time stamp linkedthereto is a piece of weather data without a user ID and a vehicle ID,the piece of linked data that is the piece of weather data having onlythe reading time stamp linked thereto is output to the integrationprocessing server 3 without any change (step S5 of FIG. 2). After that,the present process ends.

The data integration process will be described with reference to FIG. 3.The process creates an encrypted data mart using pieces of linked datainput from the data processing server 2 and outputs the createdencrypted data mart to the integrated database server 4, and is executedat the predetermined control intervals ΔT described earlier in theintegration processing server 3.

As shown in FIG. 3, a piece of linked data input from the dataprocessing server 2 is first stored in a storage region (step S20 ofFIG. 3).

It is then judged whether a time for encrypted data mart creation hascome (step S21 of FIG. 3). The creation time is set to a predeterminedtime (e.g., 24:00) of a day.

If a result of the judgment is negative (NO in step S21 of FIG. 3), thepresent process ends without doing anything.

On the other hand, if the judgment result is affirmative (YES in stepS21 of FIG. 3), an FCD-fuel-economy provisional data mart is created(step S22 of FIG. 3). The FCD-fuel-economy provisional data mart (afirst data group) is created by searching for FCDs and pieces of fueleconomy data for the last 30 days stored in the storage region using auser ID and a vehicle ID as a key and linking the FCDs and the pieces offuel economy data to each other and created as a data group (map) havingthe user ID, the vehicle ID, an FCD, a piece of fuel economy data, asampling time stamp of the piece of fuel economy data, and a readingtime stamp of the piece of fuel economy data which are linked to oneanother.

An FCD-navigation provisional data mart is then created (step S23 ofFIG. 3). More specifically, the creation of the FCD-navigationprovisional data mart (a second data group) is executed in the mannershown in FIG. 4.

As shown in FIG. 4, the FCDs and pieces of navigation data for the last30 days are compared using the user ID and the vehicle ID as a key, andit is judged whether each FCD coincides exactly in latitude andlongitude, i.e., vehicle position with any piece of navigation data(step S40 of FIG. 4).

If a result of the judgment is negative (NO in step S40 of FIG. 4),i.e., if the FCD does not coincide exactly in latitude and longitudewith any piece of navigation data, the FCD and one piece of navigationdata which are closest in latitude and longitude are linked to eachother (step S41 of FIG. 4).

On the other hand, if the judgment result is affirmative (YES in stepS40 of FIG. 4), it is judged whether the number of pieces of dataexactly coincident in latitude and longitude is one (step S42 of FIG.4).

If a result of the judgment is affirmative (YES in step S42 of FIG. 4),the FCD and the coincident piece of navigation data are linked to eachother (step S43 of FIG. 4).

On the other hand, if the judgment result is negative (NO in step S42 ofFIG. 4), and there are a plurality of pieces of data exactly coincidentin latitude and longitude, the FCD and one piece of navigation datawhich are closest in sampling time stamp are linked to each other (stepS44 of FIG. 4).

It is judged subsequently to the above-described linking processingwhether linking of all pieces of data is over (step S45 of FIG. 4). If aresult of the judgment is negative (NO in step S45 of FIG. 4), theabove-described processes are executed again.

On the other hand, if the judgment result is affirmative (YES in stepS45 of FIG. 4), i.e., when linking of the FCDs and the pieces ofnavigation data for the last 30 days is over, the present process ends.With the above-described processing, the FCD-navigation provisional datamart is created as a data group (map) having the user ID, the vehicleID, an FCD, a piece of navigation data, a sampling time stamp of thepiece of navigation data, and a reading time stamp of the piece ofnavigation data which are linked to one another.

Referring back to FIG. 3, after the FCD-navigation provisional data martis created in the above-described manner, an FCD-weather provisionaldata mart is created (step S24 of FIG. 3). More specifically, mesh codesare linked to the FCDs for the last 30 days stored in the storage regionon the basis of pieces of latitude and longitude data of the FCDs. TheFCDs and pieces of weather data are then compared. An FCD and a piece ofweather data which are coincident in mesh code with each other aresearched for, and the coincident pieces of data are linked to eachother. In the above-described manner, the FCD-weather provisional datamart (a third data group) is created as a data group (map) having theuser ID, the vehicle ID, a mesh code, an FCD, a piece of weather data, asampling time stamp of the piece of weather data, and a reading timestamp of the piece of weather data which are linked to one another.

An FCD-vehicle-condition provisional data mart is created (step S25 ofFIG. 3). The FCD-vehicle-condition provisional data mart (a fourth datagroup) is created by searching for the FCDs and pieces of vehiclecondition data for the last 30 days stored in the storage region usingthe user ID and the vehicle ID as a key and linking the FCDs and thepieces of vehicle condition data to each other and created as a datagroup (map) having the user ID, the vehicle ID, an FCD, a piece ofvehicle condition data, a sampling time stamp of the piece of vehiclecondition data, and a reading time stamp of the piece of vehiclecondition data which are linked to one another.

A data mart is created (step S26 of FIG. 3). More specifically, the datamart is created by linking the four provisional data marts created inthe above-described manner to one another using a user ID and a vehicleID as a key and created as a data group (map) having the user ID, thevehicle ID, an FCD, a piece of navigation data, a piece of weather data,a piece of vehicle condition data, a sampling time stamp, and a readingtime stamp which are linked to one another.

The data mart is then compressed into data in Lzo format using the Lzoalgorithm (step S27 of FIG. 3). After that, an encrypted data martcreation process is executed (step S28 of FIG. 3). More specifically,the encrypted data mart creation process is executed in the manner shownin FIG. 5.

As shown in FIG. 5, an encryption condition flag F_ENC is first read(step S50 of FIG. 5). The encryption condition flag F_ENC is set to anyone of “1” to “5” in accordance with the intended use (the purpose ofanalysis) of the data mart (to be described below) by an administratorof the integration processing server 3.

(a) If changes in vehicle ID at a fixed location do not interfere withdata analysis (e.g., if the traffic volume and the congestion degree ata specific intersection are desired to be analyzed), the encryptioncondition flag F_ENC is set to “1.”

(b) If changes in vehicle ID for a fixed length of time do not interferewith data analysis (e.g., if the trade area of a tourist spot or a shopis desired to be analyzed), the encryption condition flag F_ENC is setto “2.”

(c) If movement preferences of a user are desired to be analyzed, theencryption condition flag F_ENC is set to “3.”

(d) If usage in the marketplace for each vehicle type is to be analyzed,the encryption condition flag F_ENC is set to “4.”

(e) The encryption condition flag F_ENC is set to “5” for purposes otherthan the purposes (a) to (d).

It is then judged whether the read encryption condition flag F_ENC is“1” (step S51 of FIG. 5). If a result of the judgment is affirmative(YES in step S51 of FIG. 5), a cipher key is set to a combination of apart of a mesh code and a fixed key (step S52 of FIG. 5). The fixed keyis set in advance.

On the other hand, if the judgment result is negative (NO in step S51 ofFIG. 5), i.e., if F_ENC≠1, it is judged whether the encryption conditionflag F_ENC is “2” (step S53 of FIG. 5). If a result of the judgment isaffirmative (YES in step S53 of FIG. 5), the cipher key is set to acombination of a part of a sampling time stamp of a piece of navigationdata and the fixed key (step S54 of FIG. 5).

On the other hand, if the judgment result is negative (NO in step S53 ofFIG. 5), i.e., if F_ENC≠1,2, it is judged whether the encryptioncondition flag F_ENC is “3” (step S55 of FIG. 5). If a result of thejudgment is affirmative (YES in step S55 of FIG. 5), the cipher key isset to a combination of a part of the user ID and the fixed key (stepS56 of FIG. 5).

On the other hand, if the judgment result is negative (NO in step S55 ofFIG. 5), i.e., if F_ENC≠1 to 3, it is judged whether the encryptioncondition flag F_ENC is “4” (step S57 of FIG. 5). If a result of thejudgment is affirmative (YES in step S57 of FIG. 5), the cipher key isset to a combination of a part of the vehicle ID and the fixed key (stepS58 of FIG. 5).

On the other hand, if the judgment result is negative (NO in step S57 ofFIG. 5), i.e., if F_ENC=5, the cipher key is set to the fixed key (stepS59 of FIG. 5).

After the cipher key is set in accordance with a value of the encryptioncondition flag F_ENC, as described above, vehicle IDs and user IDs inthe data mart are encrypted by a predetermined encryption algorithm(e.g., SHA-256) using the cipher key (step S60 of FIG. 5).

The encrypted data mart is created by linking a piece of vehicle typedata and the encryption condition flag to the data mart having theencrypted vehicle IDs and user IDs (step S61 of FIG. 5). The piece ofvehicle type data corresponds to a part of the vehicle ID. After that,the present process ends.

Referring back to FIG. 3, after the encrypted data mart creation processis executed in the above-described manner, the encrypted data mart isoutput to the integrated database server 4 (step S29 of FIG. 3). Afterthat, the present process ends.

A data storage process will be described with reference to FIG. 6. Theprocess stores an encrypted data mart input from the integrationprocessing server 3 in the storage region in the integrated databaseserver 4, and is executed each time an encrypted data mart is input.

As shown in FIG. 6, an encrypted data mart is first read (step S80 ofFIG. 6). A vehicle type is determined on the basis of a piece of vehicletype data included in the encrypted data mart (step S81 of FIG. 6). Thevehicle type that is determined will be referred to as a determinedvehicle type hereinafter.

It is then judged whether the encryption condition flag F_ENC includedin the encrypted data mart is “1” (step S82 of FIG. 6).

If a result of the judgment is affirmative (YES in step S82 of FIG. 6),the encrypted data mart is stored as a piece of registered data in afirst region for the determined vehicle type (step S83 of FIG. 6). Afterthat, the present process ends.

On the other hand, if the judgment result is negative (NO in step S82 ofFIG. 6), i.e., if F_ENC≠1, it is judged whether the encryption conditionflag F_ENC is “2” (step S84 of FIG. 6).

If a result of the judgment is affirmative (YES in step S84 of FIG. 6),the encrypted data mart is stored as a piece of registered data in asecond region for the determined vehicle type (step S85 of FIG. 6).After that, the present process ends.

On the other hand, if the judgment result is negative (NO in step S84 ofFIG. 6), i.e., if F_ENC≠1, 2, it is judged whether the encryptioncondition flag F_ENC is “3” (step S86 of FIG. 6).

If a result of the judgment is affirmative (YES in step S86 of FIG. 6),the encrypted data mart is stored as a piece of registered data in athird region for the determined vehicle type (step S87 of FIG. 6). Afterthat, the present process ends.

On the other hand, if the judgment result is negative (NO in step S86 ofFIG. 6), i.e., if F_ENC≠1 to 3, it is judged whether the encryptioncondition flag F_ENC is “4” (step S88 of FIG. 6).

If a result of the judgment is affirmative (YES in step S88 of FIG. 6),the encrypted data mart is stored as a piece of registered data in afourth region for the determined vehicle type (step S89 of FIG. 6).After that, the present process ends.

On the other hand, if the judgment result is negative (NO in step S88 ofFIG. 6), i.e., if F_ENC=5, the encrypted data mart is stored as a pieceof registered data in a fifth region for the determined vehicle type(step S90 of FIG. 6). After that, the present process ends.

As described above, in the data registration system 1 according to thepresent embodiment, a data mart is created as a data group having anFCD, a piece of weather data, a piece of vehicle condition data, a pieceof fuel economy data, and a piece of navigation data input over thenetwork 10 and a vehicle ID and a user ID which are linked to each otherand is compressed. Additionally, an encrypted data mart is created byencrypting only vehicle IDs and user IDs in the compressed data mart byan encryption algorithm using a cypher key, and is stored as a piece ofregistered data in the storage region in the integrated database server4.

In this case, an FCD, a piece of weather data, a piece of vehiclecondition data, a piece of fuel economy data, and a piece of navigationdata are highly effective at the time of forming pieces of data relatedto a vehicle into big data and analyzing the big data, and it ispossible to efficiently register such highly effective data whileenhancing confidentiality.

Additionally, a data mart is created by creating an FCD-fuel-economyprovisional data mart, an FCD-navigation provisional data mart, anFCD-weather provisional data mart, and an FCD-vehicle-conditionprovisional data mart and collectively linking the provisional datamarts. A load at the time of data mart creation can be made smaller thanin a case where a data mart is created in one operation.

Additionally, if an FCD does not coincide exactly in latitude andlongitude, i.e., vehicle position at the time of sampling with any pieceof navigation data in the FCD-navigation provisional data mart creationprocess shown in FIG. 4, the FCD and one piece of navigation data whichare closest in latitude and longitude are linked to each other. Thus, anFCD-navigation provisional data mart can be created by linking pieces ofdata which are closest in vehicle position at the time of sampling andare estimated to be highly related to each other.

If there are a plurality of pieces of navigation data exactly coincidentin latitude and longitude with an FCD, the FCD and one of the pluralityof pieces of data which are closest in time stamp at the time ofsampling are linked to each other. Thus, an FCD-navigation provisionaldata mart can be created by linking pieces of data which are closest intime stamp at the time of sampling and are estimated to be highlyrelated to each other. In the above-described manner, the accuracy ofFCD-navigation provisional data mart creation can be enhanced.

Moreover, since a data mart is encrypted after being compressed, thesize of an encrypted data mart can be reduced. This makes it possible toincrease the number of pieces of registered data which can be stored ina storage region of the same size while enhancing the security of apiece of registered data.

Note that although the embodiment is an example which creates a datamart as a data group by creating an FCD-fuel-economy provisional datamart, an FCD-navigation provisional data mart, an FCD-weatherprovisional data mart, and an FCD-vehicle-condition provisional datamart and collectively linking the four provisional data marts, a datamart as a data group may be created by collectively linking anFCD-fuel-economy provisional data mart, an FCD-navigation provisionaldata mart, and an FCD-weather provisional data mart.

In this case, step S25 of FIG. 3 according to the embodiment may beomitted, and a data mart as a data group may be created by a methodsimilar to steps S22 to S24 and S26 described earlier.

Also, although the embodiment is an example which uses a navigationdevice as a mobile station, a mobile station according to the presentinvention is not limited to this and may be one which moves togetherwith a vehicle. For example, a handheld terminal, such as a smartphone,may be used as a mobile station.

In this case, a handheld terminal may perform data communication with anECU or a navigation device of a vehicle and receive data as a vehicle IDand/or a user ID, and a piece of data having a position (a latitude anda longitude) of the handheld terminal, a time stamp at the time ofsampling of the position, the user ID, and the like which are linked toone another may be input as a piece of movement status data from any oneof the handheld terminal and the ECU and the navigation device of thevehicle to the data processing server 2.

If a handheld terminal is used as a mobile station, a result ofperforming future route computation and the like in the handheldterminal by a user may be input as a piece of navigation data from thehandheld terminal to the data processing server 2, and a piece ofmovement status data may be input from the handheld terminal to the dataprocessing server 2, not only during a period from when an ignitionswitch of a vehicle is turned on to when the ignition switch is turnedoff but also after the ignition switch of the vehicle is turned off Inthe case of such a configuration, a data mart may be created to have,for example, a fixed value or null data as a piece of data which doesnot change while the ignition switch of the vehicle is off (e.g., apiece of fuel economy data).

Moreover, note that although the embodiment is an example which uses avehicle ID and a user ID as a piece of vehicle-identifying data, a pieceof vehicle-identifying data according to the present invention is notlimited to this and may be one for identification of at least one of avehicle and a user of the vehicle. For example, a vehicle ID or a userID may be used as a piece of vehicle-identifying data. In this case, forexample, only one of a vehicle ID and a user ID may be linked to piecesof data other than a piece of weather data, and a data mart may becreated using only one of a vehicle ID and a user ID as a key in stepsS22 to S26 of FIG. 3 in the linked data creation process in FIG. 2according to the embodiment.

On the other hand, although the embodiment is an example in which a dataregistration system according to the present invention is applied to avehicle having an internal combustion engine as a power source, the dataregistration system according to the present invention is not limited tothis and is applicable to a vehicle having something other than aninternal combustion engine as a power source. For example, the dataregistration system according to the present invention is alsoapplicable to a fuel cell vehicle, an electric vehicle, and the like.

Also, although the embodiment is an example which uses fuel economy as apiece of consumption rate data, a piece of consumption rate dataaccording to the present invention is not limited to this and may be onewhich represents an energy consumption rate of a vehicle. For example,in the case of a fuel cell vehicle, a hydrogen consumption ratecorresponds to a piece of consumption rate data. In the case of anelectric vehicle, a power consumption rate corresponds to a piece ofconsumption rate data.

Additionally, although the embodiment is an example which uses Lzoalgorithm as a compression algorithm at the time of data martcompression, the compression algorithm at the time of data martcompression is not limited to this and may be one which can compressdata. For example, Gzip or the like may be used as the compressionalgorithm at the time of data mart creation.

On the other hand, although the embodiment creates a data mart by themethod shown in FIG. 3, a data mart creation method is not limited tothis. For example, steps S25 and S26 may be omitted from the method inFIG. 3, and a data mart may be created by linking a piece of weatherdata and a piece of vehicle condition data to two provisional data martscreated in steps S22 and S23.

Although the embodiment is an example in which an encrypted data mart iscreated by encrypting a compressed data mart, and the encrypted datamart is stored as a piece of registered data in the integrated databaseserver 4, the compressed data mart may be stored in the integrateddatabase server 4 without being encrypted.

Additionally, although the embodiment is an example in which a dataregistration system is composed of three servers, a data registrationsystem may be composed of one or two servers or four or more servers.

REFERENCE SIGNS LIST

1 data registration system

2 data processing server (data reception unit)

3 integration processing server (data group creation unit and registereddata creation unit)

4 integrated database server (data storage unit)

10 network

14 vehicle

What is claimed is:
 1. A data registration system comprising: a datareception unit to which a plurality of types of data andvehicle-identifying data for identification of at least one of a vehicleand an owner of the vehicle are input through a network, the pluralityof types of data including movement status data representing atime-series movement status of a mobile station, consumption rate datarepresenting an energy consumption rate of the vehicle moving togetherwith the mobile station, navigation data representing a navigationcomputation result and a setting state in the vehicle, and weather datarepresenting weather in a region in which the mobile station existed; adata group creation unit which creates a data group having the movementstatus data, the consumption rate data, the navigation data, the weatherdata, and the vehicle-identifying data that are linked to one another; aregistered data creation unit which compresses the data group by apredetermined compression algorithm and creates registered data usingthe compressed data group; and a data storage unit which stores theregistered data in a storage region, wherein the data group creationunit creates a first data group having the vehicle-identifying data, themovement status data, and the consumption rate data that are linked toone another, a second data group having the vehicle-identifying data,the movement status data, and the navigation data that are linked to oneanother, and a third data group having the movement status data and theweather data that are linked to each other, and creates the data groupusing the first to third data groups, wherein the movement status dataand the navigation data each comprise a vehicle position at a time ofsampling as a piece of data, and if the movement status data and thenavigation data are not coincident in the vehicle position at the timeof sampling with each other in a case of creating the second data group,the data group creation unit links one piece of the movement status dataand one piece of the navigation data which are closest in the vehicleposition at the time of sampling to each other according to common userinformation data.
 2. The data registration system according to claim 1,wherein the movement status data and the navigation data each comprise atime stamp at a time of sampling and a vehicle position at the time ofsampling as pieces of data, and in a case where there are a plurality ofdata having a same vehicle position at the time of sampling in themovement status data and the navigation data in a case of creating thesecond data group, the data group creation unit links data which areclosest in the time stamp at the time of sampling to each other amongthe plurality of data.
 3. The data registration system according toclaim 1, wherein the movement status data and the navigation data eachcomprise a time stamp at the time of sampling and the vehicle positionat the time of sampling as pieces of data, and in a case where there area plurality of data having a same vehicle position at the time ofsampling in the movement status data and the navigation data in a caseof creating the second data group, the data group creation unit linksdata which are closest in the time stamp at the time of sampling to eachother among the plurality of data.
 4. The data registration systemaccording to claim 1, wherein the plurality of types of data furtherinclude vehicle condition data representing at least one of amanufacturing condition and a repair condition of the vehicle, and thedata group creation unit creates the data group by further linking thevehicle condition data in addition to the movement status data, theconsumption rate data, the navigation data, the weather data, and thevehicle-identifying data.
 5. The data registration system according toclaim 4, wherein the data group creation unit creates a first data grouphaving the vehicle-identifying data, the movement status data, and theconsumption rate data that are linked to one another, a second datagroup having the vehicle-identifying data, the movement status data, andthe navigation data that are linked to one another, a third data grouphaving the movement status data and the weather data that are linked toeach other, and a fourth data group having the vehicle-identifying data,the movement status data, and the vehicle condition data that are linkedto one another, and creates the data group using the first to fourthdata groups.
 6. The data registration system according to claim 5,wherein the movement status data and the navigation data each comprise avehicle position at a time of sampling as a piece of data, and if themovement status data and the navigation data are not coincident in thevehicle position at the time of sampling with each other in case ofcreating the second data group, the data group creation unit links onepiece of the movement status data and one piece of the navigation datawhich are closest in the vehicle position at the time of sampling toeach other.
 7. The data registration system according to claim 5,wherein the movement status data and the navigation data each comprise atime stamp at a time of sampling and a vehicle position at the time ofsampling as pieces of data, and in a case where there are a plurality ofdata having a same vehicle position at the time of sampling in themovement status data and the navigation data in a case of creating thesecond data group, the data group creation unit links data which areclosest in the time stamp at the time of sampling to each other amongthe plurality of data.
 8. The data registration system according toclaim 6, wherein the movement status data and the navigation data eachcomprise a time stamp at the time of sampling and the vehicle positionat the time of sampling as pieces of data, and in a case where there area plurality of data having a same vehicle position at the time ofsampling in the movement status data and the navigation data in the caseof creating the second data group, the data group creation unit linksdata which are closest in the time stamp at the time of sampling to eachother among the plurality of data.
 9. The data registration systemaccording to claim 1, wherein the registered data creation unit createsthe registered data by encrypting the compressed data group by apredetermined encryption algorithm.